Skip to content

Remove the directory-community feature and its MCP tools - #9

Merged
tae2089 merged 2 commits into
mainfrom
refactor/remove-community
Jul 11, 2026
Merged

Remove the directory-community feature and its MCP tools#9
tae2089 merged 2 commits into
mainfrom
refactor/remove-community

Conversation

@tae2089

@tae2089 tae2089 commented Jul 11, 2026

Copy link
Copy Markdown
Owner

What

Removes the directory-based community feature. Communities grouped nodes by directory for module-cohesion views, but that's off the project's core purpose (annotation + graph + search for preserving code context), and the derived cohesion signal duplicated what @see/@ref annotations and the call graph already express.

Changes

  • Delete internal/analysis/community.
  • Remove the list_communities, get_community, and get_architecture_overview MCP tools.
  • Drop community sections from minimal-context and related handlers.

Verification

  • go build + go vet clean; go test -tags fts5 ./... green.

First of a two-PR stack; refactor/remove-quality-analyzers stacks on top.

🤖 Generated with Claude Code

Module cohesion (community) was a coarse directory-based rollup with no
effect on retrieval or relation lookup (edges + ref annotations already
cover those), and it was the weakest-value feature per its cost. Remove:

- internal/analysis/community and the CommunityBuilder DI/interface.
- The community rebuild steps in build_or_update_graph and run_postprocess.
- The list_communities, get_community, and get_architecture_overview MCP
  tools plus their handler_graph handlers and response types.
- The community entries in get_minimal_context's tool suggestions.

run_postprocess keeps communities_count (always 0) for wire compatibility.
MCP tools: 31 -> 28. Full suite green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The project's purpose is annotation + graph + search for preserving code
context, not code-quality metrics. The large-function, dead-code, coupling,
and coverage analyzers were off-purpose, so drop them end to end:

- delete internal/analysis/{largefunc,deadcode,coupling,coverage}
- remove find_large_functions and find_dead_code MCP tools (28 -> 26)
- drop the architecture_map prompt (community + coupling) and the
  coverage/dead-code/large-function sections from review_changes,
  onboard_developer, and pre_merge_check
- remove the 4 analyzer Deps fields, DI wiring, and interface assertions
- prune dead request DTOs and decoders in handler_analysis_io.go
- update tests and guide/skill docs to match the reduced tool set

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@tae2089
tae2089 merged commit 0dd2b7f into main Jul 11, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant